Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0993

reference: 258-tree-1
name: 0993
tree-preservation-order: undefined
258-tpo-1
uprn
address-text
point: POINT (-0.935804 50.858841)
geometry: MULTIPOLYGON (((-0.935747 50.858835,-0.935750 50.858846,-0.935758 50.858856,-0.935770 50.858864,-0.935786 50.858870,-0.935803 50.858871,-0.935821 50.858870,-0.935837 50.858865,-0.935850 50.858857,-0.935858 50.858847,-0.935861 50.858836,-0.935858 50.858825,-0.935851 50.858815,-0.935838 50.858807,-0.935822 50.858801,-0.935805 50.858800,-0.935787 50.858801,-0.935771 50.858806,-0.935759 50.858814,-0.935750 50.858824,-0.935747 50.858835)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL